Goal

This meeting is just to get all OASIS related folks together to talk about what 2011 has in store for the OASIS program. There has been a large number of changes over the past year and we probably should all just get caught up.

Attendees

1. Francisco Chavez
2. Mike Kelley
3. Rich Schramm
4. Craig Okuda
5. Bob Herlien
6. Paul Coenen
7. Kevin Gomes

Topics

1. Important Dates for 2011
2. NDBC/M2 Change
3. Radio Upgrades
4. Current OASIS stats and issues
5. Future OASIS (M1) turns (process, documentation, roles and responsibilities)
6. OASIS-4 status/ocean acidification buoy
7. M0

Notes from Meeting

Important Dates for 2011

1. M2 - NDBC Early May (may 10th). NDBC/M2 Bouy
   1. code freeze 2 weeks prior to closed can testing
   2. Closed can testing 1 month
2. M1 - October 5th (late september)
3. M0 - recovery (tentative), summer (OASIS 4 upgrade)
4. O4 - March? (very tentative)
5. Upgrade

NDBC/M2 Change

1. All NDBC drawings stored online in Alfresco (https://alfresco.mbari.org/alfresco/webdav/Projects/300057_Mooring_Maint/NDBC/Drawings)
2. big question on hybrid buoy.
3. still TBD on structure of buoy and comms.
4. NDBC buoy
5. we will have to telemeter our data
6. instrumentation, memorandum has responsibilities
   1. MBARI: Nitrate, CO2, flour, radiometer on top?, O2, (bio-optical gone), pump TBD, A/D, we are responsible for maintaining our instrumentation. We are responsible telemetry, data processing. NDBC does not know if they want this data.
      1. Can we tap into their power?
   2. NDBC: Met, adcp, thermistor chain (all aspects), CTDs, GPS?
      1. How do we get data back from NDBC to MBARI? New task.
7. Controller is unknown, but O3/O4

Radio Upgrades

1. M1, 1/2 M2, M0?
2. 5 moorings.
3. Test the new hardware (assume it is what we want)
4. To run both mooring telemetry, Craig would need to put another antennae on the tower. Problematic. we don't have space.
   1. To test:
      1. Infrastructure in Mt. Toro ASAP. (buy the stuff, build) should be able to install in a month.
      2. Couple weeks of testing. Testing could be done end of February/Mid March.
      3. Testing scenario over water?
      4. Deploy the O4, ocean acidification will be the over water test.
      5. Test download and ship to SSDS.

Current OASIS Status

1. Seem to be running well.
2. Feel as if failure rate has gone up a bit.
3. More instruments failed, more controller issues,
4. M1 is running smooth?
5. Fred looks at CTD data. Ken looks at Nitrate/O2, FC looks at flourometer/radiometer
6. M2 has no ADCP, CO2
   1. M2 can needs to be swapped.
7. We need historical view of why we have failures.
   1. There is a web page with a log
   2. Is Erich not using it as detailed as Paul used to. (what is he using spreadsheet or web log?)
   3. are we updating schematics and docs?
8. How do we find problems with controllers
   1. Should have some process when can goes awry. Should all meet when something goes bad to discuss troubleshooting and FA.
9. We need more dock side testing. (currently 2 week open can, 1 week close, 3-5 working day dock side, load day)
10. How about PCO decision to move outside of process.
11. Gernot had configuration change way too late.
12. Can we split out config file for PCO2 (never have to mess with config file).
    1. Gernot said this is tough.
    2. has to be on the can, but not in oasis config file. (we need bob for this)
13. Roles:
    1. Dave French: Can prep, can test.
    2. Erich: sensor installation, setup, cables, asks rich for software uploads
    3. Rich: tracks the OASIS image that gets on mooring, writes new driver.
    4. Paul: currently doing oasis config file. Erich still coming up to speed.

1. Process
   1. start of open can test: one week before get config file setup.
   2. at that point under configuration control
   3. config should be frozen before rollout (2 days before roll out).

Future OASIS Turns

1. Process Steps
2. Documentation
   1. Bob's docs here
3. Roles and Responsibilities

1. Rich may have to build driver for pH (Ken Johnson) instrument.

OASIS-4/Ocean Acidification

1. building two for davenport and santa cruz
   1. Both will be in water by April 1st.
   2. No decisions on data path, downloads, etc.
   3. Currently three sets of hardware.
2. maybe one for M0

M0

Future

1. standardize controller and collapse data paths.